Skip to content

Conversation

@alamb
Copy link
Contributor

@alamb alamb commented Jan 9, 2026

Which issue does this PR close?

  • Closes #NNN.

Rationale for this change

One of my new years resolutions is to try and encourage / build the arrow-rs community more. Part of doing so is to lower the barrier for new contributors with clear communication and documentation.

Thus I would like to improve the main readme

What changes are included in this PR?

Update the README. See rendered preview here: https://github.com/alamb/arrow-rs/blob/alamb/improved_comms_docs/README.md

  1. Move community section to the top of the README file
  2. Clarify that most communication happens on github
Screenshot 2026-01-09 at 9 33 06 AM

Are these changes tested?

CI

Are there any user-facing changes?

@alamb alamb force-pushed the alamb/improved_comms_docs branch from 83cde1c to a233332 Compare January 9, 2026 14:32
@alamb alamb marked this pull request as ready for review January 9, 2026 21:32
### Rust Version Compatibility Policy

arrow-rs and parquet are built and tested with stable Rust, and will keep a rolling MSRV (minimum supported Rust version) that can only be updated in major releases on a need by basis (e.g. project dependencies bump their MSRV or a particular Rust feature is useful for us etc.). The new MSRV if selected will be at least 6 months old. The minor releases are guaranteed to have the same MSRV.
arrow-rs and parquet are built and tested with stable Rust, and will keep a rolling MSRV (minimum supported Rust version) that can only be updated in major releases on an as needed basis (e.g. project dependencies bump their MSRV or a particular Rust feature is useful for us etc.). The new MSRV if selected will be at least 6 months old. The minor releases are guaranteed to have the same MSRV.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

driveby wordsmithing


You can find more details about each crate in their respective READMEs.

## Arrow Rust Community
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

moved to the top and clarified

# Native Rust implementation of Apache Arrow and Apache Parquet

Welcome to the [Rust][rust] implementation of [Apache Arrow], the popular in-memory columnar format.
Welcome to the [Rust][rust] implementation of [Apache Arrow], a popular
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also note this repo has the parquet implementation

@alamb alamb added the documentation Improvements or additions to documentation label Jan 10, 2026
Co-authored-by: Jeffrey Vo <[email protected]>
@Jefffrey Jefffrey merged commit 5db4f50 into apache:main Jan 12, 2026
9 checks passed
@Jefffrey
Copy link
Contributor

Thanks @alamb

Dandandan pushed a commit to Dandandan/arrow-rs that referenced this pull request Jan 15, 2026
# Which issue does this PR close?

<!--
We generally require a GitHub issue to be filed for all bug fixes and
enhancements and this helps us generate change logs for our releases.
You can link an issue to this PR using the GitHub syntax.
-->

- Closes #NNN.

# Rationale for this change

One of my new years resolutions is to try and encourage / build the
arrow-rs community more. Part of doing so is to lower the barrier for
new contributors with clear communication and documentation.

Thus I would like to improve the main readme

# What changes are included in this PR?

Update the README. See rendered preview here:
https://github.com/alamb/arrow-rs/blob/alamb/improved_comms_docs/README.md

1. Move community section to the top of the README file
2. Clarify that most communication happens on github

<img width="1348" height="775" alt="Screenshot 2026-01-09 at 9 33 06 AM"
src="https://github.com/user-attachments/assets/fc3f6041-478d-4170-bb40-3956764a9b8d"
/>


# Are these changes tested?

CI
# Are there any user-facing changes?

<!--
If there are user-facing changes then we may require documentation to be
updated before approving the PR.

If there are any breaking changes to public APIs, please call them out.
-->

---------

Co-authored-by: Jeffrey Vo <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants